Event IDs in Windows Event Log

The table below lists the Event IDs for tasks and server events in Windows Event Log.

Some events share the same ID. With these events, the recommended way of identifying the event is to parse the notification subject. This is especially recommended if you are using third-party tools to detect and report events.

Other Event IDs
Event ID	Description
261	Any error.
262	Any warning.
263	Errors containing the specified codes.

Server Event IDs
Event ID	Description
300	Server disk usage has changed.
300	Disk utilization has changed
300	Server disk usage has reached the high threshold.
300	Server disk usage has reached the critical threshold.
300	Server disk usage has returned to normal.
320	Server system memory usage has changed.
320	Memory utilization has changed.
320	Server system memory usage has reached the high threshold.
320	Server system memory usage has reached the critical threshold.
320	Server system memory usage has returned to normal.
340	Server state has changed.

Task Event IDs
Event ID	Description
400	Task has started.
401	Full load has started.
402	Full load has completed.
403	Task has stopped after Full Load – cached changes were applied.
404	Task has stopped after Full Load – cached changes were not applied.
405	Task has stopped (other cases).
406	Task has stopped due to a non-recoverable error.
261	Task latency has exceeded the set limit.
261	Task latency is back to normal.
432	Task memory usage has exceeded the set limit.
433	Task memory usage is back to normal.
434	Task disk usage has exceeded the set limit.
435	Task disk usage is back to normal.

Table Event IDs
Event ID	Description
502	Table processing was suspended due to errors.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!

Leave your feedback here